Skip to content

Add JSON literal alias tests. #238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 10, 2019
Merged

Conversation

davidlehn
Copy link
Contributor

Tests for an implementation issue found in jsonld.js:
digitalbazaar/jsonld.js#346

@@ -0,0 +1,12 @@
{
"@context": {
"@version": 1.1,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need an explicit version here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was matching the style of the other js* tests.

Copy link
Contributor

@dlongley dlongley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I think we could (should) remove the explicit version ... or duplicate without it.

@gkellogg
Copy link
Member

Technically, it’s a 1.1 test, so @version is appropriate, but no longer necessary.

Copy link
Member

@gkellogg gkellogg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remember to run "rake" in the tests directory to make sure the HTML versions of the manifests are rebuilt.

@gkellogg
Copy link
Member

Also, expansion tests should be replicated in toRdf, as @rubensworks does not go through an intermediate expansion step; this has been the pattern for other tests.

@gkellogg gkellogg merged commit aa27ae1 into master Dec 10, 2019
@gkellogg gkellogg deleted the add-json-literal-alias-tests branch December 10, 2019 22:24
@gkellogg
Copy link
Member

For #237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants